Flash therapy treatment planning and oncology information system having dose rate prescription and dose rate mapping

ABSTRACT

A computing system comprising a central processing unit (CPU), and memory coupled to the CPU and having stored therein instructions that, when executed by the computing system, cause the computing system to execute operations to generate a radiation treatment plan. The operations include accessing a minimum prescribed dose to be delivered into and across the target, determining a number of beams and directions of the beams, and determining a beam energy for each of the beams, wherein the number of beams, the directions of the beams, and the beam energy for each of the beams are determined such that the entire target receives the minimum prescribed dose. The operations further include prescribing a dose rate and optimizing dose rate constraints for FLASH therapy, and displaying a dose rate map of the FLASH therapy.

CROSS-REFERENCE TO RELATED APPLICATION

This is a continuation application of co-pending U.S. patent application Ser. No. 16/436,762 entitled “Flash Therapy Treatment Planning and Oncology Information System having Dose Rate Prescription and Dose Rate Mapping,” by Christel Smith et al., filed Jun. 10, 2019, which is hereby incorporated by reference.

FIELD OF THE INVENTION

Embodiments of the present invention are generally related to integrated circuit structures used in memory systems that can be used by computer systems, including embedded computer systems.

BACKGROUND OF THE INVENTION

The use of radiation therapy to treat cancer is well known. Typically, radiation therapy involves directing a beam of high energy proton, photon, ion, or electron radiation (“therapeutic radiation”) into a target or target volume (e.g., a tumor or lesion).

Before a patient is treated with radiation, a treatment plan specific to that patient is developed. The plan defines various aspects of the therapy using simulations and optimizations based on past experiences. In general, the purpose of the treatment plan is to deliver sufficient radiation to the target while minimizing exposure of surrounding normal, healthy tissue to the radiation.

The planner's goal is to find a solution that is optimal with respect to multiple clinical goals that may be contradictory in the sense that an improvement toward one goal may have a detrimental effect on reaching another goal. For example, a treatment plan that spares the liver from receiving a dose of radiation may result in the stomach receiving too much radiation. These types of tradeoffs lead to an iterative process in which the planner creates different plans to find the one plan that is best suited to achieving the desired outcome.

A recent radiobiology study has demonstrated the effectiveness of delivering an entire, relatively high therapeutic radiation dose to a target within a single, short period of time, in one fraction or possible a handful of fractions. This type of treatment is referred to generally herein as FLASH radiation therapy (FLASH RT). Evidence to date suggests that FLASH RT advantageously spares normal, healthy tissue from damage when that tissue is exposed to only a single irradiation for only a very short period of time. FLASH RT thus introduces important constraints that are not considered in or achieved with conventional radiation treatment planning.

Ultra-high dose rate radiotherapy or FLASH therapy delivers high doses of radiation at very high-speed achieving dose rates of 40 Gy/s and above. Pre-clinical studies have shown that delivering radiotherapy at such ultra-high dose rates allows comparable tumor control while sparing the healthy tissue thereby reducing toxicities. The mechanism of action behind this so-called FLASH effect is still under investigation but it is becoming increasingly clear that the time a tissue is irradiated, the dose applied and therefore the dose rate are critical parameters that play a role in the FLASH effect.

Current treatment planning systems (TPS) are restricted to prescribing dose and displaying dose as a distribution overlaid on a patient's CT scan. Since dose rate and such FLASH relevant parameters are now of importance, being able to prescribe dose rate of a certain threshold to a certain specific tissue structure (healthy tissue, organs at risk, margin, and clinical tumor volume) will be crucial for treating humans with Flash. Furthermore, this input of prescription will provide clinicians and researchers valuable information that can further be correlated with biological parameters and patient outcome.

SUMMARY OF THE INVENTION

Embodiments of the present invention implement a computing system comprising a central processing unit (CPU), and memory coupled to the CPU and having stored therein instructions that, when executed by the computing system, cause the computing system to execute operations to generate a radiation treatment plan. The operations include accessing a minimum prescribed dose to be delivered into and across the target, determining a number of beams and directions of the beams, wherein the directions are determined such that the beams do not overlap outside the target, and determining a beam energy for each of the beams, wherein the number of beams, the directions of the beams, and the beam energy for each of the beams are determined such that the entire target receives the minimum prescribed dose. The operations further include prescribing a dose rate, dose rate definition, and optimizing dose rate constraints for a FLASH therapy, while displaying a dose rate map of the FLASH therapy.

In one embodiment, a physician is provided access to a drop down menu that will allow a selection of a desired dose rate definition. In one embodiment, the desired dose rate definition includes an average field dose rate, a local dose rate, a spot dose rate, an instantaneous dose rate, or a dose rate threshold.

In one embodiment, the physician can select the dose rate value after the dose rate definition is selected. In one embodiment, the physician can apply a dose rate prescription to a plurality of fields, structures, sub-structures, or groupings of voxels.

In one embodiment, the dose rate prescription is passed through a quality assurance step, where the dose rate prescription is verified before patient treatment. In one embodiment, a record and verify system records a dose and a dose rate during the time of delivery.

In one embodiment, the present invention is implemented as a non-transitory computer-readable storage medium having computer-executable instructions for causing a computing system to perform a method of generating a radiation treatment plan. The method includes accessing values of parameters from memory of the computing system, wherein the parameters comprise directions of beams to be directed into sub-volumes in a target and beam energies for the beams, accessing information that specifies limits for the radiation treatment plan, wherein the limits comprise a maximum limit on irradiation time for each sub-volume outside the target, and adjusting the values of the parameters until the irradiation time for said each sub-volume outside the target satisfies the maximum limit on irradiation time. The method further includes prescribing a dose rate and optimizing dose rate constraints for a FLASH therapy, and displaying a dose rate map of the FLASH therapy.

The foregoing is a summary and thus contains, by necessity, simplifications, generalizations and omissions of detail; consequently, those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting. Other aspects, inventive features, and advantages of the present invention, as defined solely by the claims, will become apparent in the non-limiting detailed description set forth below.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements.

FIG. 1 is a block diagram of an example of a computing system upon which the embodiments described herein may be implemented.

FIG. 2 is a block diagram illustrating an example of an automated radiation therapy treatment planning system in embodiments according to the present invention.

FIG. 3 illustrates a knowledge-based planning system in embodiments according to the present invention.

FIG. 4A is a block diagram showing selected components of a radiation therapy system upon which embodiments according to the present invention can be implemented.

FIG. 4B is a block diagram illustrating a non-coplanar arrangement of a gantry and nozzle relative to a patient support device in embodiments according to the invention.

FIG. 4C is a block diagram illustrating a coplanar arrangement of a gantry and nozzle relative to a patient support device in embodiments according to the invention.

FIG. 4D is a block diagram illustrating movement of a gantry and nozzle around a patient support device in embodiments according to the invention.

FIG. 5 is a flowchart of an example of computer-implemented operations for generating a radiation treatment plan in embodiments according to the present invention.

FIG. 6A illustrates a perspective view of an example of a beam geometry in embodiments according to the invention.

FIG. 6B illustrates a cross-sectional view of an example of a beam geometry in embodiments according to the invention.

FIG. 6C illustrates a perspective view of an example of a beam geometry in embodiments according to the invention.

FIG. 6D illustrates a cross-sectional view of an example of a beam geometry in embodiments according to the invention.

FIG. 7A illustrates a beam's eye view of a beam in embodiments according to the invention.

FIG. 7B shows a flowchart of a workflow for prescribing FLASH dose rates in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION

Reference will now be made in detail to the various embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. While described in conjunction with these embodiments, it will be understood that they are not intended to limit the disclosure to these embodiments. On the contrary, the disclosure is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the disclosure as defined by the appended claims. Furthermore, in the following detailed description of the present disclosure, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be understood that the present disclosure may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the present disclosure.

Some portions of the detailed descriptions that follow are presented in terms of procedures, logic blocks, processing, and other symbolic representations of operations on data bits within a computer memory. These descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. In the present application, a procedure, logic block, process, or the like, is conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps are those utilizing physical manipulations of physical quantities. Usually, although not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computing system. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as transactions, bits, values, elements, symbols, characters, samples, pixels, or the like.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present disclosure, discussions utilizing terms such as “determining,” “accessing,” “directing,” “controlling,” “defining,” “arranging,” “generating,” “representing,” “applying,” “adding,” “multiplying,” “adjusting,” “calculating,” “predicting,” “weighting,” “assigning,” “using,” “identifying,” “reducing,” “downloading,” “reading,” “computing,” “storing,” or the like, refer to actions and processes of a computing system or similar electronic computing device or processor (e.g., the computing system 100 of FIG. 1 ). The computing system or similar electronic computing device manipulates and transforms data represented as physical (electronic) quantities within the computing system memories, registers or other such information storage, transmission or display devices. Terms such as “dose” or “fluence” generally refer to a dose or fluence value; the use of such terms will be clear from the context of the surrounding discussion.

Portions of the detailed description that follows are presented and discussed in terms of a method. Although steps and sequencing thereof are disclosed in figures herein describing the operations of this method, such steps and sequencing are exemplary. Embodiments are well suited to performing various other steps or variations of the steps recited in the flowchart of the figure herein, and in a sequence other than that depicted and described herein.

Embodiments described herein may be discussed in the general context of computer-executable instructions residing on some form of computer-readable storage medium, such as program modules, executed by one or more computers or other devices. By way of example, and not limitation, computer-readable storage media may comprise non-transitory computer storage media and communication media. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or distributed as desired in various embodiments.

Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory or other memory technology, compact disk ROM (CD-ROM), digital versatile disks (DVDs) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can accessed to retrieve that information.

Communication media can embody computer-executable instructions, data structures, and program modules, and includes any information delivery media. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared and other wireless media. Combinations of any of the above can also be included within the scope of computer-readable media.

FIG. 1 shows a block diagram of an example of a computing system 100 upon which the embodiments described herein may be implemented. In its most basic configuration, the system 100 includes at least one processing unit 102 and memory 104. This most basic configuration is illustrated in FIG. 1 by dashed line 106. The system 100 may also have additional features and/or functionality. For example, the system 100 may also include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Such additional storage is illustrated in FIG. 1 by removable storage 108 and non-removable storage 120. The system 100 may also contain communications connection(s) 122 that allow the device to communicate with other devices, e.g., in a networked environment using logical connections to one or more remote computers.

The system 100 also includes input device(s) 124 such as keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 126 such as a display device, speakers, printer, etc., are also included.

In the example of FIG. 1 , the memory 104 includes computer-readable instructions, data structures, program modules, and the like associated with an “optimizer” model 150. However, the optimizer model 150 may instead reside in any one of the computer storage media used by the system 100, or may be distributed over some combination of the computer storage media, or may be distributed over some combination of networked computers. The functionality of the optimizer model 150 is described below.

FIG. 2 is a block diagram illustrating an example of an automated radiation therapy treatment planning system 200 in embodiments according to the present invention. The system 200 includes an input interface 210 to receive patient-specific information (data) 201, a data processing component 220 that implements the optimizer model 150, and an output interface 230. The system 200 in whole or in part may be implemented as a software program, hardware logic, or a combination thereof on/using the computing system 100 (FIG. 1 ).

In the example of FIG. 2 , the patient-specific information is provided to and processed by the optimizer model 150. The optimizer model 150 yields a prediction result. A treatment plan based on the prediction result can then be generated.

FIG. 3 illustrates a knowledge-based planning system 300 in embodiments according to the present invention. In the example of FIG. 3 , the system 300 includes a knowledge base 302 and a treatment planning tool set 310. The knowledge base 302 includes patient records 304 (e.g., radiation treatment plans), treatment types 306, and statistical models 308. The treatment planning tool set 310 in the example of FIG. 3 includes a current patient record 312, a treatment type 314, a medical image processing module 316, the optimizer model (module) 150, a dose distribution module 320, and a final radiation treatment plan 322.

The treatment planning tool set 310 searches through the knowledge base 302 (through the patient records 304) for prior patient records that are similar to the current patient record 312. The statistical models 308 can be used to compare the predicted results for the current patient record 312 to a statistical patient. Using the current patient record 312, a selected treatment type 306, and selected statistical models 308, the tool set 310 generates a radiation treatment plan 322.

More specifically, based on past clinical experience, when a patient presents with a particular diagnosis, stage, age, weight, sex, co-morbidities, etc., there can be a treatment type that is used most often. By selecting the treatment type that the planner has used in the past for similar patients, a first-step treatment type 314 can be chosen. The medical image processing module 316 provides automatic contouring and automatic segmentation of two-dimensional cross-sectional slides (e.g., from computed tomography or magnetic resonance imaging) to form a three-dimensional (3D) image using the medical images in the current patient record 312. Dose distribution maps are calculated by the dose distribution module 320, which may utilize the optimizer model 150.

In embodiments according to the present invention, the optimizer model 150 uses a dose prediction model to help shape the dose distribution. The optimizer model 150 can provide, for example, a 3D dose distribution, fluences, and associated dose-volume histograms for the current patient.

FIG. 4A is a block diagram showing selected components of a radiation therapy system 400 upon which embodiments according to the present invention can be implemented. In the example of FIG. 4A, the system 400 includes a beam system 404 and a nozzle 406.

The beam system 404 generates and transports a beam 401 to the nozzle 406. The beam 401 can be a proton beam, electron beam, photon beam, ion beam, or atom nuclei beam (e.g., carbon, helium, and lithium). In embodiments, depending on the type of beam, the beam system 404 includes components that direct (e.g., bend, steer, or guide) the beam system in a direction toward and into the nozzle 406. In embodiments, the radiation therapy system may include one or more multileaf collimators (MLCs); each MLC leaf can be independently moved back-and-forth by the control system 410 to dynamically shape an aperture through which the beam can pass, to block or not block portions of the beam and thereby control beam shape and exposure time. The beam system 404 may also include components that are used to adjust (e.g., reduce) the beam energy entering the nozzle 406.

The nozzle 406 is used to aim the beam toward various locations (a target) within an object (e.g., a patient) supported on the patient support device 408 (e.g., a chair or table) in a treatment room. A target may be an organ, a portion of an organ (e.g., a volume or region within the organ), a tumor, diseased tissue, or a patient outline.

The nozzle 406 may be mounted on or a part of a gantry (FIGS. 4B, 4C, and 4D) that can be moved relative to the patient support device 408, which may also be moveable. In embodiments, the beam system 404 is also mounted on or is a part of the gantry; in another embodiment, the beam system is separate from (but in communication with) the gantry.

The control system 410 of FIG. 4A receives and implements a prescribed treatment plan. In embodiments, the control system 410 includes a computer system having a processor, memory, an input device (e.g., a keyboard), and perhaps a display in well-known fashion. The control system 410 can receive data regarding operation of the system 400. The control system 410 can control parameters of the beam system 404, nozzle 406, and patient support device 408, including parameters such as the energy, intensity, direction, size, and/or shape of the beam, according to data it receives and according to the prescribed treatment plan.

As noted above, the beam entering the nozzle 406 has a specified energy. Thus, in embodiments according to the present disclosure, the nozzle 406 includes one or more components that affect (e.g., decrease, modulate) the energy of the beam. The term “beam energy adjuster” is used herein as a general term for a component or components that affect the energy of the beam, in order to control the range of the beam (e.g., the extent that the beam penetrates into a target), to control the dose delivered by the beam, and/or to control the depth dose curve of the beam, depending on the type of beam. For example, for a proton beam or an ion beam that has a Bragg peak, the beam energy adjuster can control the location of the Bragg peak in the target. In various embodiments, the beam energy adjuster 407 includes a range modulator, a range shifter, or both a range modulator and a range shifter. That is, when the term “beam energy adjuster” is used, then the element being discussed may be a range modulator, a range shifter, or both a range modulator and a range shifter.

FIG. 4B is a block diagram illustrating a non-coplanar arrangement of a gantry 420 and nozzle 406 relative to a patient support device 408 in embodiments according to the invention. FIG. 4C is a block diagram illustrating a coplanar arrangement of a gantry 420 and nozzle 406 relative to a patient support device 408 and also illustrating movement of the gantry and nozzle around the patient support device in embodiments according to the invention. FIG. 4D is a block diagram illustrating movement of the gantry 420 and nozzle 406 around the patient support device 408 in embodiments according to the invention. This movement can occur in either the non-coplanar arrangement or the coplanar arrangement.

FIG. 5 is a flowchart 500 of an example of computer-implemented operations for generating a radiation treatment plan in embodiments according to the present invention. The flowchart 500 can be implemented as computer-executable instructions (e.g., the optimizer model 150 of FIG. 1 ) residing on some form of computer-readable storage medium (e.g., using the computing system 100 of FIG. 1 ).

In intensity modulated radiation therapy (IMRT) such as intensity modulated particle therapy (IMPT), beam intensity is varied across each treatment region (target) in a patient. Depending on the treatment modality, the degrees of freedom available for intensity modulation include beam shaping (collimation), beam weighting (spot scanning), and angle of incidence (which may be referred to as beam geometry). These degrees of freedom lead to an effectively infinite number of potential treatment plans, and therefore consistently and efficiently generating and evaluating high-quality treatment plans is beyond the capability of a human and relies on the use of a computing system, particularly considering the time constraints associated with the use of radiation therapy to treat ailments like cancer, as well as the large number of patients that are undergoing or need to undergo radiation therapy during any given time period.

In block 502 of FIG. 5 , a prescribed dose to be delivered into and across the target is determined. Each portion of the target can be represented by at least one 3D element known as a voxel; a portion may include more than one voxel. A portion of a target or a voxel may also be referred to herein as a sub-volume; a sub-volume may include one or more portions or one or more voxels. As will be described in detail below, each portion or voxel may receive radiation from one or more beams delivered from different directions. The prescribed dose defines, for example, a dose value, or a minimum dose value and a maximum dose value, for each portion or voxel of the target. In embodiments, the prescribed dose is the same for all portions (sub-volumes or voxels) of the target, such that a uniform dose is prescribed for the entire target.

In block 504, directions (e.g., gantry angles relative to the patient or target, or nozzle directions relative to the patient or target) for delivering beams into the target are determined. The beams can be proton beams, electron beams, photon beams, ion beams, or atom nuclei beams. The operation of determining beam directions can include determining the number of beams (the number of directions from which beams are to be delivered). The beams' paths may or may not overlap within the target, and may or may not overlap outside the target. In general, when generating the radiation treatment plan, one goal is to determine beam paths that minimize the irradiation time of each sub-volume or voxel of the tissue outside the target. Ideally, each sub-volume or voxel outside the target is intersected, at most, by only a single beam. If some overlap between beam paths is permitted, then ideally each sub-volume or voxel outside the target is intersected by not more than two beams, with most intersected by only a single beam. In embodiments, as one means of achieving the aforementioned goal, the beam directions are determined such that the total amount of overlap between the beams' paths is minimized outside the target. In one such embodiment, the directions are determined such that the paths of the beams overlap within the target and such that the total amount of overlap of the beams' paths outside the target is less than the total amount of the overlap of the beams' paths within the target. In another such embodiment, the directions are determined so that the paths of the beams do not overlap at all outside the target. The beams' paths can lie within the same plane, or they can be in different planes. Additional information is provided in conjunction with FIGS. 6A, 6B, 6C, and 6D.

Any number of other factors may be considered when determining the beam directions. These factors may include the shape and size (e.g., height H and width W, or diameter) of the beam in the beam's eye view (see FIG. 7A). These factors may also include, for example, the amount or type of healthy tissue that a beam will be traveling through. That is, one beam direction may be more favorable than another if it travels a shorter distance through healthy tissue or avoids passing through a vital organ and may be weighted accordingly.

In block 506 of FIG. 5 , a beam energy or intensity is determined for each of the directions (for each of the beams). The beam energy or intensity for each direction is determined such that the predicted or calculated cumulative doses (e.g., doses calculated using the optimizer model 150 of FIG. 1 ) at locations inside the target satisfy the prescribed dose as defined in block 502. As noted, beam paths may or may not overlap in the target; if the beams' paths overlap in the target, then the beam energy or intensity for each direction is determined such that the predicted or calculated cumulative doses (e.g., doses calculated using the optimizer model 150 of FIG. 1 ) at locations inside the target where the beams' paths overlap satisfy the prescribed dose as defined in block 502. In embodiments, a beam includes a number of beam segments or beamlets. In one or more such embodiments, a maximum energy (e.g., 80 MeV) for the beam is specified, and an energy for each of the beam segments is determined as a percentage (100 percent or less) or equivalent fraction of the maximum beam energy. In general, beams can have the same energy or different energies, and each beam can have a range of energies. Thus, different energies or intensities can be delivered in different directions, and different energies or intensities can be delivered in each direction. Additional information is provided in conjunction with FIG. 7A.

While the operations in blocks 502, 504, and 506 of FIG. 5 are presented as occurring in series and in a certain order, the present invention is not so limited. The operations may be performed in a different order and/or in parallel, and they may also be performed in an iterative manner, as the number of beams (and accordingly, the number of directions), the beam directions, and the beam energies or intensities (and/or beam segment energies or intensities) used to deliver the prescribed dose are interrelated. As noted above, because of the different parameters that need to be considered, the range of values for those parameters, the interrelationship of those parameters, the need for treatment plans to be effective yet minimize risk to the patient, and the need to generate high-quality treatment plans quickly, the use of the optimizer model 150 executing consistently on the computing system 100 (FIG. 1 ) for radiation treatment planning as disclosed herein is important.

The discussion to follow refers to beams, targets, doses, and other elements or values. The discussion below is in the context of modeled elements and calculated values in the treatment planning tool set 310 and the optimizer model 150 (FIG. 3 ), unless otherwise noted or made clear in the discussion.

FIG. 6A illustrates a perspective view of an example of a beam geometry in embodiments according to the invention. In the example of FIG. 6A, the beams (exemplified by beam 602) are in the same plane. The beams can be proton beams, electron beams, photon beams, ion beams, or atom nuclei beams. Each beam can deliver a relatively high dose in a relatively short period of time. For example, in embodiments, each beam can deliver doses sufficient for FLASH RT (e.g., at least four (4) grays (Gy) in less than one second, and as much as 20 Gy or 50 Gy or more in less than one second). In embodiments, the range is 0.01-500 Gy. As described herein, each beam can include one or more beam segments or beam lets. In this example, the beams' paths overlap only within the target 604, and do not overlap outside the target in the surrounding tissue 606.

In the example of FIG. 6A, the beam 602 (for example) is illustrated as passing completely through the target 604. For beams that have a Bragg peak (e.g., proton beams and ion beams), the ranges of the beams can be controlled so that the beam does not pass completely through the target, as will be described further below.

Although multiple beams are shown in FIG. 6A, this does not mean that all beams are necessarily delivered at the same time or in overlapping time periods, although they can be. The number of beams delivered at any one time depends on the number of gantries or nozzles in the radiation treatment system (e.g., the radiation treatment system 400 of FIG. 4A) and on the treatment plan.

FIG. 6B illustrates a cross-sectional view of an example of a beam geometry in embodiments according to the invention. In this example, the beams (exemplified by beams 605 and 606) overlap only within the target and are in the same plane. The figure depicts the beams in overlapping fashion to demonstrate that each portion of the target 604 receives a dose of radiation. The beams can be proton beams, electron beams, photon beams, ion beams, or atom nuclei beams. In the example of FIG. 6B, the beams are illustrated as not extending beyond the distal edge of the target 604 (as would be the case for proton or ion beams, for example); however, the invention is not so limited. Each beam can deliver a relatively high dose in a relatively short period of time. For example, each beam can deliver doses sufficient for FLASH RT.

For implementations in which the beams have a Bragg peak, such as a proton beam or an ion beam, the dose delivered by a beam (or beam segment) is not necessarily uniform along the entire length of the beam path through the target 604. Thus, for example, for a proton or ion beam, the dose delivered by the beam 605 at the proximal portion (or edge) 608 of the target 604 may be different from (e.g., less than) the dose delivered by that beam at the distal portion (or edge) 610 of the target (here, proximal and distal are with reference to the source of the beam 605). The same can be said for each proton or ion beam.

The dose delivered to each portion of the target 604 is cumulative, based on the number of beams that are delivered to and through that portion. For example, the portions of the target 604 covered by the beams 605 and 606 receive a total dose that is the sum of the dose delivered by the beam 605 and the dose delivered by the beam 606. In embodiments, the energies of the beams (beam segments) are accurately determined so that, even though the dose along each beam (or beam segment) is not uniform, a uniform cumulative dose distribution is achieved within and across the target 604.

FIG. 6C illustrates a perspective view of an example of a beam geometry in embodiments according to the invention. In the example of FIG. 6C, the beams (exemplified by beam 612) are in different planes. As described herein, each beam can include one or more beam segments or beam lets. In this example, the beams' paths overlap only within the target 604, and do not overlap outside the target in the surrounding tissue 606. Although multiple beams are shown in the figure, all beams are not necessarily delivered at the same time or in overlapping time periods as mentioned above. The beams can be proton beams, electron beams, photon beams, ion beams, or atom nuclei beams. Each beam can deliver a relatively high dose in a relatively short period of time. For example, each beam can deliver doses sufficient for FLASH RT.

FIG. 6D illustrates a cross-sectional view of an example of a beam geometry in embodiments according to the invention. In this example, the beams (exemplified by beams 621, 622, and 623) overlap only within the target and are in the same plane. While three beams are illustrated, the invention is not so limited. As described herein, each beam can include one or more beam segments or beamlets. In this example, the beams' paths overlap only within the target 604, and do not overlap outside the target in the surrounding tissue 606. Although multiple beams are shown in the figure, all beams are not necessarily delivered at the same time or in overlapping time periods as mentioned above. The beams can be proton beams, electron beams, photon beams, ion beams, or atom nuclei beams. Each beam can deliver a relatively high dose in a relatively short period of time. For example, each beam can deliver doses sufficient for FLASH RT.

In the example of FIG. 6D, the beams 621, 622, and 623 intersect at the sub-volume 630, other sub-volumes in the target 604 receive doses from two of the beams, other sub-volumes in the target receive doses from only one of the beams, and yet other sub-volumes do not receive a dose. The directions and/or numbers of beam can be varied over a number of treatment sessions (that is, fractionated in time) so that a uniform dose is delivered across the target.

As mentioned above, for implementations that use proton beams or ion beams, the dose delivered by each beam at the respective proximal portion (or edge) of the target 604 may be different from (e.g., less than) the dose delivered by that beam at the respective distal portion (or edge) of the target (as before, proximal and distal are with reference to the source of the beam).

The dose delivered to each portion of the target 604 is cumulative, based on the number of beams that are delivered to and through that portion. Not all beams are depicted in the figures for simplicity; in general, the number of beams is sufficient to achieve a uniform cumulative dose distribution within the target 604.

In general, the surface of a target can be viewed as having a number of discrete facets. From this perspective, for beams other than photon beams, each incident beam is orthogonal to each facet such that the beams do not overlap outside the target. In the case of photon beams, each incident beam is parallel to the facet and does not overlap other beams outside the target.

FIG. 7A illustrates a beam's eye view (BEV) of a beam 702 in embodiments according to the invention. That is, FIG. 7A illustrates a cross-section of a beam. The beams of FIGS. 6A, 6B, 6C, and 6D are examples of the beam 702. The beam 702 is illustrated as being rectangular in shape having a height H and width W. However, the invention is not so limited, and the beam 702 can have virtually any regular or irregular cross-sectional (e.g., BEV) shape. For example, the shape of the beam 702 can be defined using an MLC that blocks a portion or portions of the beam. Different beams can have different shapes.

In the FIG. 7A embodiment, the beam 702 includes a number of beam segments or beam lets (that also may be referred to as spots) exemplified by beam segments 704, 706, and 708. A maximum energy (e.g., 80 MeV) is specified for the beam 702, and an energy level is defined for each of the beam segments as a percentage or fraction of the maximum energy. In essence, each of the beam segments is weighted in terms of its energy level; some beam segments are weighted to have a higher energy level than other beam segments. By weighting the energy per beam segment, in effect the intensity of each beam segment is also weighted. The energy per beam segment is defined so that the beam segment will deliver a fraction of the prescribed dose such that, in combination with the other beam segments in the beam, and in combination with the other beams (and beam segments), a uniform (homogeneous) cumulative dose that satisfies the prescribed dose will be delivered within and across the volume of the target. The defined energy level or intensity can be realized for each beam segment using the beam energy adjuster 407 of FIG. 4A.

Each beam segment can deliver a relatively high dose in a relatively short period of time. For example, each beam segment can deliver at least 4 Gy in less than one second, and may deliver as much as 20 Gy or 50 Gy or more in less than one second. The energy or intensity of each beam segment can be controlled using the beam energy adjuster 407 of FIG. 4A so that the beam segment has sufficient energy to reach the distal edge of the target.

In operation, in embodiments, the beam segments are delivered sequentially. For example, the beam segment 704 is delivered to the target (turned on) and then turned off, then the beam segment 706 is turned on then off, then the beam segment 708 is turned on then off, and so on. Each beam segment may be turned on for only a fraction of a second (on the order of milliseconds).

A FLASH prescription capability in a TPS and OIS (e.g., oncology information system) so that a physician can for example prescribe a certain dose rate based of a selected dose-rate definition (e.g., for example voxel-specific, contour-specific, global beam dose rate, etc.) dose rate threshold or irradiation time for a specific tissue structure. As research in this area progresses, the ability to determine which parameters have the most impact on patient outcome and refine FLASH prescriptions adjusting and optimizing with dose rate parameters becomes important. In addition, dose rate or irradiation times per voxel in 3D or 4D will be displayed similarly to how dose is displayed in the TPS today.

In the prior art, there are currently no dose rate, irradiation time or such parameters included in prescribing a treatment within a TPS or OIS. Making such information available to prescribe dose rate, optimize on dose rate constraints and displaying the dose rate map will allow the clinician to prescribe FLASH therapy in a reliable way while gathering information on the impact of those parameters on patient outcome.

For example, a clinician can decide to prescribe FLASH therapy to a lung cancer patient and determine depending on how dose rate is defined, that they need 90% of the normal lung to be irradiated at FLASH dose rate above 40 Gy/s. As more is learned from pre-clinical studies, perhaps it may be determined brain structures require higher dose rates in order to achieve the FLASH effect, so perhaps for a brain case, the clinician will want to prescribe that normal brain should receive a minimum dose rate of 100 Gy/s. They will also be able to visualize on the dose rate map if the prescription is achieved and make decisions on the course of treatment.

FIG. 7B shows a flowchart of a workflow for prescribing FLASH dose rates in accordance with one embodiment of the present invention. In one embodiment, the workflow for prescribing dose rate would begin in the physician's intent stage, just prior to treatment planning. At that stage, the physician can select relevant treatment parameters such as the prescription dose and fractionation schedule.

The method 750 begins with step 752, where the physician selects relevant parameters. The physician will have access to a drop down menu that will allow him or her to select the desired dose rate definition. Parameters include, for example, average field dose rate, local dose rate, spot dose rate, instantaneous dose rate, computed with active time or total time, or any other specific definition of biologically relevant dose rate, or time-depended flux pattern, as that information becomes available through pre-clinical research.

In step 754, the physician selects a desired dose rate definition. Once the dose rate definition is selected, the physician can select the dose rate value (40 gy/sec to 120 gy/sec) and above.

In step 756, the physician selects a desired dose rate value. The physician can also select treatment modalility (e.g., Bragg-Peak, Transmission, or a hybrid approach).

In step 758, the physician selects a treatment modality. The physician can apply the dose rate prescription to any field, structure, sub-structure, or groupings of voxels.

In step 760, the physician specifies plan statistical parameters. The physician can specify plan statistical parameters such as, for example, 90% of the voxels in healthy lung shall receive dose rate of x and above and no less than 70% of dose delivered at or above 40 Gy/s.

In step 762, a flash prescription is translated into a deliverable plan. In treatment planning the clinician will be able to translate the flash prescription into a deliverable plan. This means optimizing for dose to target simultaneously with optimizing for the dose rate prescription.

In step 764, quality assurance is performed on the dose rate prescription. The dose rate prescription gets passed through to a QA step, where now dose delivered and dose rate delivered is verified before patient treatment.

In step 766, the final step is the OIS acts as the record and verify system during the time of delivery. Recording and verifying both dose and dose-rate delivered for each fraction of the patients treatment. It should be noted that in one embodiment, offline adaptations may occur as well, with dose accumulation and dose-rate tracking. Should the dose or dose-rate deviate from physicians intent, the plan will be sent for re-planning.

The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed, and many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims appended hereto and their equivalents. 

What is claimed is:
 1. A computing system comprising: a processor; and memory coupled to the processor and having stored therein instructions that, when executed by the computing system, cause the computing system to execute operations to generate a radiation treatment plan, the operations comprising: accessing a minimum prescribed dose to be delivered into and across a target; determining a number of beams and directions of the beams, wherein each beam of the beams has a Bragg peak; optimizing dose rate constraints for a FLASH therapy; and displaying a dose rate map of the FLASH therapy.
 2. The computing system of claim 1, wherein access is provided to a menu that allows a selection of a desired dose rate definition.
 3. The computing system of claim 2, wherein the desired dose rate definition comprises an average field dose rate, a local dose rate, a spot dose rate, or an instantaneous dose rate.
 4. The computing system of claim 2, wherein a dose rate value can be selected after the dose rate definition is selected.
 5. The computing system of claim 2, wherein a dose rate prescription can be applied to a plurality of fields, structures, sub-structures, or groupings of voxels.
 6. The computing system of claim 5, wherein the dose rate prescription is passed through a quality assurance step, where the dose rate prescription is verified before patient treatment.
 7. The computing system of claim 5, wherein a record and verify system records a dose and a dose rate during the time of delivery.
 8. A non-transitory computer-readable storage medium having computer-executable instructions for causing a computing system to perform a method of generating a radiation treatment plan, the method comprising: accessing values of parameters from memory of the computing system, wherein the parameters comprise directions of beams, wherein each of the beams has a Bragg peak; accessing information that specifies limits for the radiation treatment plan, wherein the limits comprise a maximum limit on irradiation time for each sub-volume outside a target; adjusting the values of the parameters until the irradiation time for said each sub-volume outside the target satisfies the maximum limit on irradiation time; optimizing dose rate constraints for a FLASH therapy; and displaying a dose rate map of the FLASH therapy.
 9. The non-transitory computer-readable storage medium of claim 8, further comprising: providing access to a menu that will allow a selection of a desired dose rate definition.
 10. The non-transitory computer-readable storage medium of claim 9, wherein the desired dose rate definition comprises an average field dose rate, a local dose rate, a spot dose rate, or an instantaneous dose rate.
 11. The non-transitory computer-readable storage medium of claim 9, further comprising: selecting the dose rate value after the dose rate definition is selected.
 12. The non-transitory computer-readable storage medium of claim 9, further comprising: applying a dose rate prescription to a plurality of fields, structures, sub-structures, or groupings of voxels.
 13. The non-transitory computer-readable storage medium of claim 12, further comprising: passing the dose rate prescription through a quality assurance step, where the dose rate prescription is verified before patient treatment.
 14. The non-transitory computer-readable storage medium of claim 12, further comprising: recording a dose and a dose rate during the time of delivery.
 15. A computing system comprising: a processor; and memory coupled to the processor and having stored therein instructions that, when executed by the computing system, cause the computing system to execute operations to generate a radiation treatment plan, the operations comprising: accessing a minimum prescribed dose to be delivered into and across a target; determining a number of beams and directions of the beams, wherein each beam of the beams has a Bragg peak, and wherein the directions are determined such that the beams do not overlap outside the target and overlap inside the target; providing a drop down menu that allows a selection of a desired dose rate definition; optimizing dose rate constraints for a FLASH therapy; and displaying a dose rate map of the FLASH therapy.
 16. The computing system of claim 15, wherein the desired dose rate definition comprises an average field dose rate, a local dose rate, a spot dose rate, or an instantaneous dose rate.
 17. The computing system of claim 15, wherein a dose rate value can be selected after the dose rate definition is selected.
 18. The computing system of claim 15, wherein a dose rate prescription can be applied to a plurality of fields, structures, sub-structures, and groupings of voxels.
 19. The computing system of claim 18, wherein the dose rate prescription is passed through a quality assurance step, where the dose rate prescription is verified before patient treatment.
 20. The computing system of claim 18, wherein a record and verify system records a dose and a dose rate during the time of delivery. 